- The blanket "every gap is a false-negative, never a false-positive" claim
  was wrong for one row: block-scoped variable shadowing (issue #5) is a
  documented false-positive risk, not a false-negative one — verified by
  reproducing it against the built binary. Carved out the exception in both
  supported-scope.md and limitations.md instead of overclaiming.
- The command-comparison table said flaglint-go has no `init`/`completion`;
  it actually does ship a working `completion` command (Cobra's stock
  boilerplate, not bespoke) — split the row and corrected it. `init` really
  doesn't exist yet.

Signed-off-by: Krishan Kant Sharma <krishansharma0327@gmail.com>

…trict-types and baseline counts

Every identity-resolution gap listed as "not resolved yet" on the
flaglint-go Limitations and Supported Scope pages has actually been
closed (verified directly against the flaglint-go issue tracker):
chained factory-call-then-method (#20), method values (#6), interface
satisfaction (#15), block-scoped shadowing (#5), factory returning a
wrapper type (#16), and nested go.mod files (#17). These pages were last
updated right before that work landed.

- limitations.md / supported-scope.md: mark all six as resolved (noting
  which layer resolves each — Phase 1 default vs. opt-in --strict-types),
  add two newer Phase-1 mechanisms these pages never mentioned at all
  (a struct field declared *ld.LDClient with no observed construction,
  and a composite literal directly initializing a package-level var),
  and state plainly that zero identity-resolution gaps are currently
  tracked.
- identity-model.md: add worked examples for both newer Phase-1
  mechanisms above, plus a new "Phase 2 — --strict-types" section
  (interface satisfaction, transitive factory wrapping, cross-function
  method-value forwarding) that didn't exist on this page at all before.
- index.md: same corrections to the "what flaglint-go does/doesn't do"
  summary — it previously named method values and interface satisfaction
  as open gaps.
- cli/{scan,audit,validate}.md: --strict-types wasn't documented as a
  flag anywhere on the site despite being available on all three
  commands since it shipped; added to each page's options table.
  audit.md's baseline JSON example was also missing the "schemaVersion"
  and "counts" fields flaglint-go now emits; validate.md's Baseline Mode
  section gains a note on what "counts" actually catches (a brand-new
  duplicate of an already-baselined call, not just a brand-new
  fingerprint).

Verified: `npm run build` completes cleanly (90 pages), spot-checked the
rendered Limitations page's output directly.

Signed-off-by: Krishan Kant Sharma <krishansharma0327@gmail.com>